home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.19971216-19980424 / 000396_news@newsmaster….columbia.edu _Tue Apr 7 20:45:18 1998.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id UAA02368
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Tue, 7 Apr 1998 20:45:18 -0400 (EDT)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id UAA01265
  7.     for kermit.misc@watsun; Tue, 7 Apr 1998 20:45:17 -0400 (EDT)
  8. Path: news.columbia.edu!panix!news.eecs.umich.edu!nntprelay.mathworks.com!howland.erols.net!netnews.com!news.maxwell.syr.edu!news.mel.connect.com.au!not-for-mail
  9. From: Ross Irvine <rirvine@netlink.com.au>
  10. Newsgroups: comp.protocols.kermit.misc
  11. Subject: Re: Msdos Kermit & Windows 95 DOS prompt.
  12. Date: Wed, 08 Apr 1998 10:45:33 +1000
  13. Organization: Victorian BreastScreen Registry
  14. Lines: 12
  15. Message-ID: <352AC8AD.95BA4CE8@netlink.com.au>
  16. References: <3529944E.1ACDB07A@netlink.com.au> <SGYKcvvLy6si@cc.usu.edu>
  17. NNTP-Posting-Host: kermit.netlink.com.au
  18. Mime-Version: 1.0
  19. Content-Type: text/plain; charset=us-ascii
  20. Content-Transfer-Encoding: 7bit
  21. X-Mailer: Mozilla 4.04 [en] (Win95; I)
  22. Cache-Post-Path: kermit.netlink.com.au!unknown@dl009.netlink.com.au
  23. Xref: news.columbia.edu comp.protocols.kermit.misc:8599
  24.  
  25. Joe Doupnik wrote:
  26. >         MS-DOS Kermit is telling the truth. Your serial port is not responding
  27. > as a real serial port when MSK tests it. This could be from IRQ conflicts,
  28. > or devices overlapping the Port address range of the serial port, or the
  29. > hardware comes up uninitialized and requires coaxing to speak clearly.
  30. >         SET PORT 1 is identical to SET PORT COM1.
  31.  
  32. That what I originally thought, but I can run kermit again without doing
  33. a thing and it works. There is no device conflict for com1.
  34. Very strange!
  35.  
  36. Regards..